Yasmin product designer
Case study 03Employee volunteering · BT Group

My Volunteering

Bringing a fragmented volunteering service into a single platform.

My Volunteering, platform homepage, final UI The previous volunteering portal homepage
Fig. 01, The My Volunteering platform homepage, final UI
01Overview

BT gives every employee three days of paid volunteering leave a year, but the service around it was scattered across systems, and only around half of the volunteering that happened was ever recorded. As the sole product designer, I reframed what began as a systems-integration brief into a platform strategy: one destination for discovering, applying for and recording volunteering.

RoleSole Product Designer
Duration9 months
CompanyBT Group
ScopeProduct strategy · End-to-end experience design · Service design · Stakeholder management · Requirements shaping · Usability testing · Design delivery
02Problem

Half the volunteering was invisible

Only around half of employees' volunteering activity was being recorded, leaving BT unable to report reliably on a benefit it actively promotes. The initial brief framed this as a data problem: integrate MyHR with the volunteering portal and the records would follow.

The journey told a different story. Information lived across a legacy portal and SharePoint, opportunities were promoted through different channels, and application processes varied from one opportunity to the next. The real challenge was a navigable service, from discovery through to recording, not just better data capture.

From the research
“I tried to book volunteering through the portal but gave up and arranged it with my manager instead.”
Discovery research, BT employee
03Insight

The reporting issue wasn’t a broken screen, it was a disconnected service

01
Recording happens after the value

The assumption was that recording was too cumbersome. In reality, it happens after the volunteering is done, and its value accrues to the business, not the individual. It gets forgotten, not avoided.

02
Fragmentation compounds at every step

Each hand-off between SharePoint, the portal and email was a drop-out point. No single screen was broken; the journey between them was.

03
Design for memory, not diligence

A single destination that surfaces approved leave and prompts recording at the right moment removes the reliance on users remembering, the shift from integration exercise to platform strategy.

04Process

Reframing a reporting problem into a service opportunity

I challenged the narrow MyHR-integration scope with evidence: a service blueprint of the as-is journey, marking every drop-out point from awareness through to recording. It showed the fragmentation plainly, and made the case for consolidating information, discovery, applications and recording into one platform.

The volunteering team aligned quickly, because the platform served their participation goal too. Crucially, the reframe kept a clear MVP, a bigger vision didn't mean a bigger first release.

Volunteering service blueprint, as-is state, mapping the journey from awareness to recording
Fig. 02, The as-is service blueprint: five journey stages, backstage operations, and the drop-out points that made the case for one platform

Designing a platform, not a collection of pages

The architecture was structured around system dependencies rather than page templates. A homepage and Explore area consolidated the content scattered across SharePoint and the legacy portal, backed by a unified opportunity database, BT-promoted and local opportunities searchable together, with shared categorisation, filtering and reporting.

Because charities apply in different ways, the platform supports multiple application methods, email, MS Forms, third-party sites, so the service could scale without forcing every provider through one funnel.

Reducing reliance on user memory

Working with solution architects and HR, I integrated approved volunteering-leave data into the platform itself. Approved leave is surfaced automatically as an unrecorded entry, and contextual email reminders cover the cases where MyHR constraints applied.

Instead of expecting users to remember to report, the system proactively supports completion, designed around real behaviour rather than ideal behaviour.

05Results

Better data, a fraction of the effort

- 87% reduction

in monthly reporting effort for the volunteering team, down from around half a day.

Reliable data

Rogue and erroneous recurring entries largely eliminated, restoring confidence in the numbers.

+3.1% year-on-year

Recorded volunteering entries year on year, on a cleaner and more trustworthy baseline.

14/14 users

completed core journeys with strong confidence in usability testing before launch.

Register and record my hours, approved leave surfaced as an unrecorded entry
01, Approved leave surfaced, unrecorded
Recording your hours, the activity form
02, Hours recorded in one form
Register and record my hours, activity recorded
03, Entry recorded automatically
01, Approved leave surfaced, unrecorded02, Hours recorded in one form03, Entry recorded automatically

The launched platform brought the whole journey, discovery, application, leave and recording, into one place. In testing, colleagues described it as simple and elegant; stakeholders saw the benefit of the integration through better data almost immediately.

The most important outcome for me was the reframe itself: treating a reporting problem as a service problem. The blueprint that made that argument is now the definitive documentation of how BT's volunteering service works.

From usability testing
“I like the simplicity. It looks elegant, simple, not too congested.”
Usability testing participant, BT employee
06Features built

Features built

01
Unified volunteering platform
02
Opportunity discovery ecosystem
03
Centralised opportunity database
04
Opportunity submission and approval workflow
05
End-to-end volunteering journey
06
MyHR integration
07
Automated activity recording
08
Reporting and data-quality improvements
Next case study
My Wellbeing
Read next →
My Wellbeing portal
© 2026 Yasmin Osman, Product Designer Good design is complexity, clicking into place.